Description of Change

This pull request proposes a modification to the behavior of the RefreshView control.

Currently, setting the IsRefreshing property to true in the RefreshView control not only enables the loading animation but also triggers the associated command.

To address this issue, the proposed change involves separating the responsibilities of the IsRefreshing property to achieve the desired behavior:

1. IsRefreshing will solely control the animation enable/disable feature.
2. Command execution will only be executed when the user initiates the refresh through the control UI or at their discretion within their view model.

But why is separating the responsibilities necessary?

As @janseris notes,

We could set IsRefreshing=true in the ViewModel instead of calling ReloadData to achieve the correct behavior but that is not a good idea because we cannot assume from the ViewModel that setting property IsRefreshing will call the ReloadData method by coincidence (we don't know in ViewModel that IsRefreshing is bound to a RefreshView control in the View which also by coincidence calls ReloadData via a registered Command).

We could possibly rename the IsRefreshing property to better reflect its behavior, but this would create a breaking change. Some possibilities would be:

1. IsAnimating
2. IsAnimationInProgress
3. IsRefreshingAnimationActive
4. IsRefreshAnimationVisible

If this change is accepted, I will also update the documentation which states:

Manually setting the IsRefreshing property to true will trigger the refresh visualization, and will execute the ICommand defined by the Command property.

Source: learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/refreshview?view=net-maui-7.0

Issues Fixed

Fixes #6456
Fixes #1171